Skip to content

fix: unify trust tier labels in scoreboard dump API#19

Open
DreadPirateRobertz wants to merge 1 commit intogastownhall:mainfrom
DreadPirateRobertz:fix/unify-trust-tier
Open

fix: unify trust tier labels in scoreboard dump API#19
DreadPirateRobertz wants to merge 1 commit intogastownhall:mainfrom
DreadPirateRobertz:fix/unify-trust-tier

Conversation

@DreadPirateRobertz
Copy link
Copy Markdown
Contributor

Summary

  • The /api/scoreboard/dump endpoint exposed trust_level (raw integer) without a trust_tier string, forcing consumers to implement their own tier-name mapping
  • Added trust_tier field to RigRow, computed server-side from stamp weighted scores using the same DeriveTrustTier() function the scoreboard uses
  • All consumers now get consistent tier labels instead of rolling their own mapping

Test plan

  • All 13 Go test packages pass
  • New assertions verify trust_tier derivation in both commons and API tests

🤖 Generated with Claude Code

The /api/scoreboard/dump endpoint exposed trust_level (raw integer from
rigs table) without a trust_tier string, forcing consumers to implement
their own tier mapping. The homepage used "DRIFTER" for level 0 while
the scoreboard API used "outsider" via DeriveTrustTier().

Add trust_tier field to RigRow, computed server-side from stamp weighted
scores using the same DeriveTrustTier() function the scoreboard uses.
All consumers now get consistent tier labels.

Co-Authored-By: Claude Opus 4.6 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant